Device, system, and method for persisting network registration rejection causes

ABSTRACT

A device, system, and method persists network registration rejection causes. The method is performed at a device connected to a network and comprising a temporary memory and a persistent memory, the device using the data stored in the temporary memory when performing network registration operations. When a power cycle is detected, the method includes determining whether there is persistent data in the persistent memory for a first attempt to register with the network prior to the power cycle, the persistent data including a rejection cause for the first attempt. When there is the persistent data in the persistent memory, the method includes determining whether the persistent data is valid for a second attempt to register with the network after the power cycle. When the persistent data is valid, the method includes generating and storing cause data based on the persistent data in the temporary memory prior to the second attempt.

BACKGROUND INFORMATION

A user equipment (UE) may be configured to establish a connection to atleast one of a plurality of different networks or types of networks aswell as with other UEs to perform a variety of different functionalitiesvia the connection. For example, the UE may connect to a first type ofnetwork (e.g., Long Term Evolution (LTE) network) to communicate withanother UE through the network connection (e.g., a user of the UE mayperform a voice call or transmit a text to another user of another UE).In another example, the UE may connect to a second type of network(e.g., WiFi network) to receive browser data at a higher rate of dataexchange. In a further example, the UE may directly connect to a furtherUE using a short-range communication protocol (e.g., BlueTooth).

When the UE performs connection operations to register with a network,the registration process may fail where the UE is rejected for a varietyof different reasons. While a baseband processor and the correspondingfunctionality on a transceiver remain active, data corresponding to thisrejection cause may be stored for use by these components in a temporarymanner (e.g., in a random access memory (RAM)). Accordingly, whenfurther attempts to register with the network are to be performed, therejection cause in the data that is temporarily stored may be used todetermine whether the attempt is to be made. For example, the data mayindicate a rejection cause from the network that indicates anysubsequent attempt would also result in the registration with thenetwork to fail. In this manner, the UE may determine that theoperations are not to be performed, which conserves power usage.However, there are a variety of reasons that the temporarily stored dataincluding the rejection causes are not available or deleted, whichprompts the UE to perform connection operations that result inregistration failures and use additional power.

SUMMARY

The exemplary embodiments are directed to a method, comprising: at adevice that is configured to establish a connection to a network, thedevice comprising a memory arrangement including a temporary memory anda persistent memory, the device using the data stored in the temporarymemory when performing operations associated with registering with thenetwork: when a power cycle is detected, determining whether there ispersistent data in the persistent memory corresponding to a result froma first attempt to register with the network prior to the power cycle,the persistent data including a rejection cause received from thenetwork for the first attempt; when there is the persistent data in thepersistent memory, determining whether the persistent data is valid touse in a second attempt to register with the network after the powercycle; when the persistent data is valid, generating cause data based onthe persistent data; and storing the cause data in the temporary memoryprior to performing the second attempt.

The exemplary embodiments are directed to a device, comprising: atransceiver; a memory arrangement including a temporary memory and apersistent memory; a baseband processor configured in conjunction withthe transceiver to establish a connection to a network, wherein thebaseband processor uses data stored in the temporary memory whenperforming operations associated with registering with the network; andan applications processor configured to detect a power cycle of thebaseband processor, when the power cycle is detected, the applicationsprocessor determining whether there is persistent data in the persistentmemory corresponding to a result from a first attempt to register withthe network prior to the power cycle, the persistent data including arejection cause received from the network for the first attempt,wherein, when there is the persistent data in the persistent memory, theapplications processor determines whether the persistent data is validto use in a second attempt to register with the network after the powercycle, wherein, when the persistent data is valid, the applicationsprocessor generates cause data based on the persistent data, andwherein, the applications processor stores the cause data in thetemporary memory prior to the baseband processor performing the secondattempt.

The exemplary embodiments are directed to a method, comprising: at adevice that is configured to establish a connection to a network, thedevice comprising a memory arrangement including a temporary memory anda persistent memory, the temporary memory deleting data stored thereinafter a power cycle, the persistent memory persisting data storedtherein after the power cycle, the device using the data stored in thetemporary memory when performing operations associated with registeringwith the network: transmitting a request to the network to register withthe network; receiving a response to the request from the network; whenthe response includes a rejection cause indicating the request isrejected, storing the rejection cause in both the temporary memory andthe persistent memory, wherein, after a power cycle, the rejection causeis capable of being used in a further request to the network to registerwith the network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a network arrangement according to the various exemplaryembodiments described herein.

FIG. 2 shows a user equipment according to the various exemplaryembodiments described herein.

FIG. 3 shows a method for persisting rejection cause data whileregistering with a network according to the various exemplaryembodiments described herein.

FIG. 4 shows a method for utilizing persistent rejection cause dataprior to registering with a network according to the various exemplaryembodiments described herein.

DETAILED DESCRIPTION

The exemplary embodiments may be further understood with reference tothe following description and the related appended drawings, whereinlike elements are provided with the same reference numerals. Theexemplary embodiments are related to a device, system, and method forpersisting a rejection cause from a network registration attempt.Specifically, a user equipment (UE) may attempt to connect to a networkwhich includes a registration procedure and, for any of a variety ofreasons, the registration may fail. Although the rejection cause for thefailed registration attempt may be stored temporarily, when a subsequentregistration attempt is made, the rejection cause may becomeunavailable. However, the circumstances in which the subsequentregistration attempt is being made may be substantially similar to theprior registration attempt and not user initiated. In thesecircumstances, knowing the previous rejection cause may allow the UE toconserve power by not performing operations that lead to anotherregistration failure. Accordingly, the exemplary embodiments provide amechanism to persist the rejection cause and subsequently use thepersistent rejection cause for further registration attempts, whenapplicable.

Initially, it is noted that the exemplary embodiments are described withregard to a UE. However, the UE is only exemplary. The exemplaryembodiments may be utilized with any device that may establish aconnection with one or more networks and configured with the hardware,software, and/or firmware to exchange and process data with any of theseone or more networks. Therefore, the UE as described herein is used torepresent any device.

It is also noted that the exemplary embodiments are described withregard to the UE having a companion UE. When the UE and the companion UEare connected to one another over a short-range communication pathway,the UE may receive data via the companion UE. When the UE and thecompanion are not connected, the UE may receive data over a connectednetwork directly (instead of through the companion UE). However, the useof the UE and the companion UE is only exemplary. The exemplaryembodiments may be utilized for any UE (with or without a companion UE)and represent any device.

It is further noted that the exemplary embodiments are described withregard to a failure of a registration procedure in which a rejectioncause is provided by the network. However, the use of the registrationprocedure, the failure of the registration procedure, and the rejectioncause are only exemplary. The exemplary embodiments may be modifiedand/or utilized with any procedure in which a result of the procedure ispersisted for use in determining how a subsequent procedure is to beperformed.

With developments to UEs as well as further types of UEs beingintroduced (e.g., with the Internet of Things (IoT)), the manner inwhich the UEs may communicate with networks or other UEs has expanded.For example, a first UE may be linked to a second UE as companions.Specifically, the first UE may be a wearable while the second UE may bea smartphone which is the wearable's companion. While the wearable andthe smartphone are within range of one another within the limits of ashort-range communication protocol, the wearable and the smartphone maycommunicate such that data being received by the smartphone may berelayed to the wearable (e.g., an incoming call or text received on thesmartphone may be relayed to the wearable). In this manner, the wearablemay conserve a limited power supply by using only the short-rangecommunication protocol instead of having to associate with and monitorone or more networks. That is, components of the UE such as a basebandprocessor and associated functionality/operations performed on atransceiver for the network may be deactivated.

The UE (e.g., the wearable) may also be configured to associate andexchange data with one or more networks independently without thecompanion UE. For example, when the UE is separated from the companionUE (e.g., greater than the distance of the short-range communicationprotocol), the UE may include the hardware, software, and firmwarerequired to connect to one or more networks such as a cellular network.However, as noted above, the UE may have a limited power supply (e.g.,even more limited than the companion UE) and connecting with networksmay drain more power than only using the short-range communicationprotocol. Specifically, performing initial connection operationsincluding a registration procedure may utilize additional power.However, previous attempts in performing this registration procedure mayprovide insight to subsequent attempts in performing this registrationprocedure. Accordingly, the exemplary embodiments are configured toconsider and take advantage of this historical information.

FIG. 1 shows a network arrangement 100 according to the exemplaryembodiments. The network arrangement 100 includes UEs 110-114. Thoseskilled in the art will understand that the UEs 110-114 may be any typeof electronic component that is configured to communicate via a network,e.g., mobile phones, tablet computers, desktop computers, smartphones,phablets, embedded devices, wearables, Cat-M devices, Cat-M1 devices,MTC devices, eMTC devices, other types of IoT devices, etc. It shouldalso be understood that an actual network arrangement may include anynumber of UEs being used by any number of users and being associatedwith any number of these users where the user may be associated with oneor more of the UEs. That is, the example of three (3) UEs 110-114 isonly provided for illustrative purposes.

Each of the UEs 110-114 may be configured to communicate directly withone or more networks. In this example, the networks with which the UEs110-114 may wirelessly communicate are a legacy radio access network(RAN) 120 (e.g., a first type of cellular network), a LTE RAN (LTE-RAN)122 (e.g., a second type of cellular network), and a wireless local areanetwork (WLAN) 124 (e.g., a WiFi network). However, it should beunderstood that the UEs 110-114 may also communicate with other types ofnetworks and may also communicate using a wired connection. For example,other types of networks may include Wideband Code Division MultiplexingAccess (WCDMA) RAN, Global System for Mobile communication (GSM) RAN,3G/4G RAN, new generation (NG) RANs including 5G, etc. With regards tothe exemplary embodiments, the UEs 110-114 may establish a connectionwith one or more of the legacy RAN 120, the LTE-RAN 122, and the WLAN124. For example, the UEs 110-114 may have a legacy chipset, a LTEchipset, and/or a WiFi chipset that are used to communicate with thelegacy RAN 120, the LTE-RAN 122, and/or the WLAN 124, respectively. Theuse of three (3) networks is only exemplary and there may be any othernumber of networks with which the UEs 110-114 may communicate.

Each of the UEs 110-114 may also be configured to communicate with theother UEs 110-114 without using the networks 120-124. For example, asillustrated, the UE 110 may communicate with the UE 112 using ashort-range communication protocol such as BlueTooth. Thus, if the UE110 and the UE 112 are within a proximity of one another (e.g., within adistance in which BlueTooth communications may be performed), the UE 110and the UE 112 may exchange data. In a specific exemplary embodiment, ifthe short-range communication protocol is being used, the UE 110 and theUE 112 may have a companion relationship. In the companion relationship,the UE 110 may utilize only the short-range communication protocolwithout connecting to any of the networks 120-124 while the UE 112 mayconnect to one or more of the networks 120-124 and relay data exchangedbetween the networks 120-124 and the UE 112 to the UE 110 over theshort-range communication pathway. However, it is again noted that theuse of a companion relationship is only exemplary and the UE 110 mayconnect to one or more of the networks 120-124 whether or not the UE 110is within range of communicating with the UE 112 over the short-rangecommunication pathway.

The legacy RAN 120 and the LTE-RAN 122 are portions of cellular networksthat may be deployed by cellular providers (e.g., Verizon, AT&T, Sprint,T-Mobile, etc.). These networks 120 and 122 may include, for example,base client stations (Node Bs, eNodeBs, HeNBs, etc.) that are configuredto send and receive traffic from UEs that are equipped with theappropriate cellular chip set. The WLAN 124 may include any type ofwireless local area network (WiFi, Hot Spot, IEEE 802.11x networks,etc.).

In addition to the networks 120-124, the network arrangement 100 alsoincludes a cellular core network 130, the Internet 140, an IP MultimediaSubsystem (IMS) 150, and a network services backbone 160. The cellularcore network 130 may be considered to be the interconnected set ofcomponents that manages the operation and traffic of the cellularnetwork. The cellular core network 130 also manages the traffic thatflows between the cellular network and the Internet 140. The IMS 150 maybe generally described as an architecture for delivering multimediaservices to the UEs 110-114 using the IP protocol. The IMS 150 maycommunicate with the cellular core network 130 and the Internet 140 toprovide the multimedia services to the UEs 110-114. To use the featuresof the IMS 150, the UEs 110-114 may register with the IMS through aregistration procedure via one of the networks 120, 122, 124. Thenetwork services backbone 160 is in communication either directly orindirectly with the Internet 140 and the cellular core network 130. Thenetwork services backbone 160 may be generally described as a set ofcomponents (e.g., servers, network storage arrangements, etc.) thatimplement a suite of services that may be used to extend thefunctionalities of the UEs 110-114 in communication with the variousnetworks. The network services backbone 160 may interact with the UEs110-114 and/or the networks 120, 122, 124, 130, 140 to provide theseextended functionalities.

The exemplary embodiments are directed to the UE 110 being capable ofconnecting to one of the networks 120, 122, 124 and also capable ofconnecting to the UE 112 over a short-range communication protocol.Specifically, the UE 110 may be in a companion relationship with the UE112. For illustrative purposes, the exemplary embodiments are describedwith the UE 110 connecting to the LTE-RAN 122 but it is again noted thatthe use of the LTE-RAN 122 is only exemplary and the exemplaryembodiments may be utilized with the UE 110 connecting to any type ofnetwork.

While not connected to the UE 112, the UE 110 may connect to the LTE-RAN122 using its baseband processor and associated functionality/operationson its transceiver (collectively referred to herein as “baseband”). Whenthe baseband of the UE 110 attempts to register with the LTE-RAN 122,the LTE-RAN 122 may determine if the UE 110 is a valid device that iscapable and/or allowed to connect to the LTE-RAN 122. If a determinationis made that the UE 110 is invalid, the LTE-RAN 122 may reject theregistration based on a rejection cause which is provided to the UE 110.

In a first example, the rejection cause may be a non-fatal cause asdefined by 3GPP 24.008 and 24.301. The non-fatal cause may be based on agiven location area (LA) (e.g., a set of base stations grouped tooptimize signaling operations for networks in general), a routing area(RA) (e.g., an equivalent of the LA for packet-switched domains), ortracking area (TA) (e.g., an equivalent of the LA and/or RA for theLTE-RAN 122). The non-fatal cause may also be specified in 3GPP 24.008and 24.301. For example, the non-fatal cause may be specified as #12,which indicates that the location of the UE 110 is not allowed.Specifically, the #12 non-fatal cause may be sent from the LTE-RAN 122to the UE 110 if the UE 110 requests an update in location in an areawhere the UE 110 is not allowed to operate based on a subscription. Inanother example, the non-fatal cause may be specified as #13, whichindicates that a roaming functionality on the UE 110 is not allowed inits current location. Specifically, the #13 non-fatal cause may be sentfrom the LTE-RAN 122 to the UE 110 if the UE 110 requests an update inlocation in an area of the LTE-RAN 122 which offers roaming to the UE110 if indicated in a subscription. In a further example, the non-fatalcause may be specified as #15, which indicates that there are nosuitable cells or base stations in the area where the UE 110 iscurrently located. Specifically, the #15 non-fatal cause may be sentfrom the LTE-RAN 122 to the UE 110 if the UE 110 requests an update inlocation in an area where the UE 110 is not allowed to operate based ona subscription and when the UE 110 should find another allowed area inthe LTE-RAN 122.

In a second example, the rejection cause may be a fatal cause. The fatalcause may be based on features of a subscriber identity module (SIM) oruniversal SIM (USIM) of the UE 110. For illustrative purposes, the SIMis used to represent any identification of the user and/or the UE 110with a corresponding subscription including the USIM. The fatal causemay also be specified in 3GPP 24.008 and 24.301. For example, the fatalcause may be specified as #2, which indicates that the internationalmobile subscriber identity (IMSI) is not known in the home locationregister (HLR) of an area where the UE 110 is located. In anotherexample, the fatal cause may be specified as #3, which indicates thatthe UE 110 is illegal.

Specifically, the SIM of the UE 110 may be determined to be illegal ifan identity included in the SIM of the UE 110 is not acceptable or theUE 110 fails to pass an authentication check. In a further example, thefatal cause may be specified as #6, which indicates that the type ofequipment of the UE 110 is not allowed by the LTE-RAN 122 in the areawhere the UE 110 is located. In yet another example, the fatal cause maybe specified as #7, which indicates that a general packet radio service(GPRS) is not allowed where an IMSI attach request is provided from theUE 110 to the LTE-RAN 122, but the LTE-RAN 122 determines that the GPRSis not allowed for the UE 110. In an additional example, the fatal causemay be specified as #8, which indicates that the GPRS and non-GPRS arenot allowed for the UE 110.

It is noted that the above example of rejection causes and thecorresponding codes are only exemplary. There may be other rejectioncauses for the LTE-RAN 122 or other rejection causes related to othertypes of networks. However, all the types of rejection causes may begrouped into the above two general categories, non-fatal and fatal.

When the UE 110 receives a rejection cause from the LTE-RAN 122, the UE110 is configured to perform several operations. When the UE 110receives a rejection cause that is a non-fatal cause, the UE 110 may beconfigured to store the non-fatal cause into a temporary or volatilememory such as a random access memory (RAM) of the baseband.Specifically, the non-fatal cause may be stored in a correspondingforbidden list. The UE 110 may also be configured to initiate a timer(e.g., 12 hours) for the temporarily stored non-fatal cause, which uponexpiry, results in the non-fatal cause to be deleted from the basebandmemory. The non-fatal cause may also be removed or deleted based onother factors such as when the device or baseband is power cycled orwhen a SIM card is physically removed from the UE 110. However, whilethe non-fatal cause is still temporarily stored and the timer has notexpired, the UE 110 may utilize the non-fatal cause to avoid attempts ofthe registration procedure on the forbidden LA, RA, or TA as indicatedin the non-fatal cause.

When the UE 110 receives a rejection cause that is a fatal cause, the UE110 may be configured to mark the SIM as illegal for packet switched(PS) and non-PS services based on the fatal cause. In a substantiallysimilar manner as the non-fatal cause, the UE 110 may store this markingof the SIM as illegal into the temporary or volatile memory of thebaseband. Thus, while the SIM card physically remains in the UE 110 orthe UE/baseband is not rebooted or power cycled, the UE 110 may utilizethe fatal cause to avoid attempts of the registration procedure.However, if the SIM card is physically removed or the UE/baseband isrebooted/power cycled, the fatal cause may be deleted and unavailable.

As noted above, the rejection cause (both non-fatal causes and fatalcauses) may be stored in a temporary memory of the baseband. However,the rejection cause that is stored in the temporary memory may bedeleted when the UE 110 or the baseband of the UE 110 is power cycled.When the UE 110 is in a companion relationship, the UE 110 mayexperience power cycling of the baseband more frequently than if the UE110 were not in the companion relationship. Specifically, the UE 110 inthe companion relationship may be configured to prioritize utilizing theshort-range communication protocol rather than a network connection tothe LTE-RAN 122. For example, using the short-range communicationprotocol may use less power than the network connection for the UE 110to conserve power. Accordingly, when the short-range communicationprotocol is determined to be available, the UE 110 may be configured toswitch to the direct connection to the UE 112. However, by switchingfrom the network connection to the short-range communication protocol,the baseband is deactivated. When the baseband becomes re-activated, thebaseband is power cycled. In this manner, whenever the baseband becomesdeactivated/re-activated (e.g., power cycled), particularly when theshort-range communication protocol is used for the companionrelationship, the rejection cause stored in the temporary memory of thebaseband may be lost. When previously stored rejection causes aredeleted, the UE 110 proceeds with performing connection operations suchas those used with a registration procedure as if the rejection causewere never determined, even if the circumstances surrounding theprevious rejection have not significantly changed.

Given the above aspects of the registration procedure, a result in whicha rejection cause is provided from the LTE-RAN 122 and stored in atemporary memory, and the baseband of the UE 110 being power cycled,there may be scenarios where the UE 110 may benefit from persisting therejection cause even after the baseband has power cycled for use insubsequent registration procedure attempts. In an exemplary scenario,the baseband may be in a state where the baseband has a list offorbidden LA/RA/TA due to a non-fatal cause received from the LTE-RAN122 or in a state where the LTE-RAN 122 has invalidated the SIM bysending a fatal cause. Accordingly, the baseband of the UE 110 may beactivated and used in attempting a registration procedure to the LTE-RAN122. As noted above, the UE 110 may be configured to store the rejectioncause in the temporary memory when received from the LTE-RAN 122.

Subsequently, the UE 110 may be positioned in proximity or otherwisecapable of utilizing the companion relationship with the UE 112 suchthat the short-range communication protocol is used. As noted above,when this operation occurs, the baseband of the UE 110 may deactivate orswitch off completely to conserve power and any data exchange isperformed over the short-range communication protocol. As will bedescribed in detail below, this operation may be described as a non-usertriggered deactivation. This deactivation of the baseband will cause thedata that is stored in the temporary memory of the baseband (e.g., theinformation associated with the forbidden LA/RA/TA) to be lost.

At a later time, the UE 110 may re-activate the baseband. For example,the UE 110 may be positioned such that the companion relationship is notcapable of being used and the short-range communication protocol isunavailable with the UE 112. Accordingly, the baseband may bere-activated. Again, as will be described in detail below, the basebandbeing re-activated in this manner may be a non-user triggeredactivation. As noted above, a power cycle of the baseband may result indata in a temporary memory to be deleted such as any rejection causesthat were stored. Therefore, if the UE 110 has any forbidden LA/RA/TAbefore the power cycle, this information that was stored is erased. Ifthe UE 110 had the SIM invalidated by the LTE-RAN 122 before the powercycle, the marking of the SIM may be deleted.

In either case, the rejection cause may be deleted/unavailable andsubsequent registration procedures may be performed without any priorhistorical information of the results of previous registrationprocedures. When there has been no significant change to thecircumstances of the UE 110, the registration procedure attempts may beredundant and unnecessary because the saved non-fatal or fatal rejectioncause may occur as an earlier non-fatal or fatal rejection cause. Whenthe UE 110 moves into and out of proximity of the companion UE 112, theUE 110 may repeatedly perform unsuccessful registration attempts. Therepeated unsuccessful registration attempts entail performing aplurality of operations that dissipate the power supply of the UE 110,and there also may be a performance degradation from increasing the timetaken to establish a stable network service.

To compensate for scenarios such as the one described above, theexemplary embodiments provide a mechanism to persist a stored rejectcause to be used in considering how to proceed with performingconnection operations including a registration procedure. The mechanismaccording to the exemplary embodiments may initially be configured toperform an additional storage operation. Specifically, the rejectioncause that is stored in the temporary memory of the baseband may also bestored in a persistent or non-volatile memory of the UE 110. The UE 110may also store other information (e.g., SIM) with respect to a usersubscription (e.g., IMSI, ICCID, etc.). The UE 110 may further storetime related information (e.g., a timestamp) used to help identifydetails/validity of persistent information. When stored in thepersistent memory, even if the UE 110 is rebooted, the baseband is powercycled, and/or the SIM is physically removed/replaced, the rejectioncause may still be available in the persistent memory. Therefore, when anon-user triggered deactivation/re-activation (e.g., a non-usertriggered power cycle) is performed on the baseband such that therejection cause in the temporary memory is deleted, the mechanismaccording to the exemplary embodiments may be used to use the persistentrejection cause. As will be described in detail below, the UE 110 maymatch the details of the persistent rejection cause and other details todetails of current circumstances of the UE 110. Specifically, when thepersistent rejection cause is a non-fatal cause, the match may be to acurrently camped LA/RA/TA of the UE 110. When the persistent rejectioncause is a fatal cause, the match may be to the IMSI or other SIMdetails.

It is noted that the mechanism according to the exemplary embodimentsuses non-user triggered deactivation/re-activation operations. That is,the power cycle of the baseband or otherwise deletion of the storedrejection cause is from operations that are automatically performed byapplications on the UE 110 rather than actions or operations performedby a user. Thus, the exemplary embodiments may be used when the reasonfor the power cycle of the baseband is based on a non-userdeactivated/re-activated operation. Examples of user-activatedoperations that cause the power cycle on the baseband may includephysically removing the SIM (and subsequently replacing with the sameSIM or new SIM), manually rebooting the baseband or the UE 110, etc.When the power cycle of the baseband is determined to be from auser-activated operation, the mechanism according to the exemplaryembodiments may assume that any previous rejection cause is to beignored for performing subsequent registration procedures. That is, apersistent rejection cause may be deleted or omitted from considerationbecause the user may have intended for the rejection cause to be deletedand a new connection attempt to be performed.

It is also noted that the use of the power cycle of the baseband or theUE 110 being the reason for the rejection cause to be deleted from thetemporary memory is only exemplary. Those skilled in the art willunderstand that there are a variety of reasons for the rejection causeor the temporary memory in general to delete stored data. For example,the above noted user-activated operations may also cause the stored datain the temporary memory to be deleted. Accordingly, the exemplaryembodiments may be configured to persist the rejection cause whenever arejection cause is received. The exemplary embodiments are alsoconfigured to selectively determine when the persistent rejection causeis to be used based on the reason that the stored data corresponding tothe rejection cause has been deleted (e.g., non-user activated operationor user activated operation).

FIG. 2 shows the UE 110 of the network arrangement 100 of FIG. 1according to the exemplary embodiments. Specifically, the UE 110 isconfigured to execute a plurality of applications that performfunctionalities to persist rejection cause information from at least oneprior registration procedure attempt and utilize this persistentrejection cause when appropriate. The UE 110 may represent anyelectronic device that is configured to perform wireless functionalitiesand may be representative of one or more of the UEs 110-114 (examples ofwhich are noted above). The UE 110 may include a processor 205, a memoryarrangement 210, a display device 215, an input/output (I/O) device 220,a transceiver 225, and other components 230. The other components 230may include, for example, an audio input device, an audio output device,a battery that provides a limited power supply, a data acquisitiondevice, ports to electrically connect the UE 110 to other electronicdevices, etc.

The processor 205 may be configured to execute a plurality ofapplications of the UE 110. For example, the applications may include aconnection application 235, a recording application 240, and a stateapplication 245. As will be described in further detail below, theconnection application 235 may be configured to perform connectionoperations to connect to the LTE-RAN 122. The recording application 240may be configured to perform storage operations in a temporary andpersistent manner. The state application 245 may be configured todetermine a reason for the baseband to become activated.

It should be noted that the above noted applications each being anapplication (e.g., a program) executed by the processor 205 is onlyexemplary. The functionality associated with the applications may alsobe represented as a separate incorporated component of the UE 110 or maybe a modular component coupled to the UE 110, e.g., an integratedcircuit with or without firmware. For example, the integrated circuitmay include input circuitry to receive signals and processing circuitryto process the signals and other information. In addition, in some UEs,the functionality described for the processor 205 is split among twoprocessors, a baseband processor and an applications processor. Theexemplary embodiments may be implemented in any of these or otherconfigurations of a UE. For example, the connection application 235 maybe implemented on a baseband processor whereas the recording application240 and the state application 245 may be implemented on an applicationsprocessor.

The memory 210 may be a hardware component configured to store datarelated to operations performed by the UE 110. The memory 210 mayinclude a temporary memory 210A and a persistent memory 210B. As thoseskilled in the art will understand, the temporary memory 210A may be anyvolatile memory in which data stored therein does not persist when apower cycle is experienced. In contrast, the persistent memory 210B maybe any non-volatile memory in which data stored therein persists when apower cycle is experienced. For example, the temporary memory 210A maybe a RAM while the persistent memory 210B may be a flash memory.

The display device 215 may be a hardware component configured to showdata to a user while the I/O device 220 may be a hardware component thatenables the user to enter inputs. It should be noted that the displaydevice 215 and the I/O device 220 may be separate components orintegrated together such as a touchscreen. The transceiver 225 may be ahardware component configured to exchange data with a base stationassociated with the LTE-RAN 122 (e.g., an evolved Node B (eNB)).Accordingly, the transceiver 225 may operate on a variety of differentfrequencies or channels (e.g., set of consecutive frequencies).Therefore, the transceiver 225 may include one or more components toenable the data exchange with the various networks and UEs. For example,a first component of the transceiver 225 (that is part of the baseband)may enable a BlueTooth connection to be established with the UE 112 anda second component of the transceiver 225 may enable a LTE connection tobe established with the LTE-RAN 122. One or more antennas (not shown)may be coupled to these one or more components of the transceiver 225 toenable the transceiver 225 to operate on the various frequency bands.

As described above, the connection application 235 may be configured toperform connection operations to connect to the LTE-RAN 122. Theconnection operations may be any operation used to establish aconnection between the UE 110 and the LTE-RAN 122 such that data may beexchanged with an associated eNB of the LTE-RAN 122 and utilize services(e.g., with the IMS 150). For example, the registration procedure may beincluded in the connection operations. The connection operations mayinclude providing information from the SIM of the UE 110 and/or otheridentifying information (e.g., capabilities of the UE 110, an operatingsystem of the UE 110, etc.).

The connection application 235 may also have an allocated section of thetemporary memory 210A to be used in performing the connectionoperations. The allocation in the temporary memory 210A may be performedusing any mechanism as those skilled in the art will understand. It isnoted that whenever the connection application 235 is activated andbeing used, the allocation in the temporary memory 210A may be performedand the corresponding section may be known. With the connectionapplication 235 having an allocated section in the temporary memory210A, the connection application 235 may access the allocated sectionand use data stored therein.

Specifically, the allocated section may be used to store historicalinformation such as results from prior registration procedure attempts.When there is no data yet stored in the allocated section, theconnection application 235 may assume that there is no historicalinformation and proceed in performing the connection operations withthis assumption.

The recording application 240 may be configured to perform storageoperations in a temporary and persistent manner. Specifically, therecording application 240 may store results of registration procedureattempts. As noted above, the recording application 240 may beconfigured with a first storage operation in which data corresponding tothe results of the registration procedure attempts is stored in thetemporary memory 210A, particularly in the allocated section of theconnection application 235. Thus, while the baseband of the UE 110 isactivated, the data corresponding to the results of the registrationprocedure attempts may be available in the allocated section of thetemporary memory 210A.

The recording application 240 may be configured with a second storageoperation according to the exemplary embodiments. In addition to storingthe data corresponding to the results of the registration procedureattempts in the allocated section of the temporary memory 210Aassociated with the connection application 235, the recordingapplication 240 may further store the data corresponding to the resultsof the registration attempts in the persistent memory 210B. Therecording application 240 may store the data in the persistent memory210B in a manner corresponding to whether the result includes anon-fatal cause (e.g., a corresponding code) or a fatal cause (e.g., acorresponding code). For example, when the result includes a non-fatalcause, the recording application 240 may store data corresponding to alist of forbidden LA/RA/TA received from the LTE-RAN 122 in thetemporary memory 210A as well as store this data in the persistentmemory 210B along with other corresponding information at the time thisresult occurred (e.g., a timestamp, an associated timer for keeping thedata in the temporary memory 210A when no intervening operation isperformed such as a power cycle, the IMSI, an integrated circuit cardidentifier (ICCID), other SIM details perceived as necessary, etc.). Inanother example, when the result includes a fatal cause, the recordingapplication 240 may store data corresponding to a marking that the SIMis invalidated by the LTE-RAN 122 as well as store this data in thepersistent memory 210B along with other SIM details (e.g., IMSI, ICCID,etc.).

Using the above operations, the UE 110 may perform an initial part ofthe mechanism according to the exemplary embodiments. That is, wheneverattempts of the registration procedure are made by the UE 110 whenconnecting to the LTE-RAN 122, the UE 110 may redundantly store resultsof these attempts in both the temporary memory 210A and the persistentmemory 210B where the storing in the persistent memory 210B may furtherinclude any associated information.

The state application 245 may be configured to determine a reason forthe baseband to become activated. As noted above, the state application245 may be performed by a higher level component such as theapplications processor. Accordingly, the state application 245 maymonitor the baseband and be aware of the type ofdeactivation/re-activation (e.g., power cycle) performed on thebaseband. Specifically, the state application 245 may determine whethera power cycle was activated with a user activated operation or anon-user activated operation.

As noted above, the state application 245 may identify when a useractivated operation is performed as the reason for the baseband to bepower cycled such that data stored in an allocated section of thetemporary memory 210A is deleted. In a first example, the stateapplication 245 may detect when a power input is received from the user.For example, the I/O device 220 may include a power input that the usermay use to activate the UE 110 from a deactivated state or deactivatethe UE 110 from an activated state. In a particular example, the usermay reboot the UE 110 which results in a power cycle. In a secondexample, the state application 245 may detect that if the SIM card hasbeen physically removed and/or replaced (either with the same SIM cardor a new SIM card). As the physical removal of the SIM card entails theuser performing this action, the state application 245 may identify theuser activated operation as the cause for the power cycle of thebaseband.

The state application 245 may also identify when a non-user activatedoperation is performed as the reason for the baseband to be powercycled. The non-user activated operation may be the reason any time abaseband power cycle is performed without any user activated operation.That is, the introduction of any user activated operation in the powercycle may automatically qualify as the reason being user activated. Forexample, if the deactivation aspect of the power cycle were performedfrom a non-user activated operation (e.g., availability of using thecompanion relationship over the short-range communication protocol) butthe re-activation aspect of the power cycle were performed from a useractivated operation (e.g., manually rebooting the UE 110), the reasonfor the power cycle may be considered a user activated operation. Incontrast, if the deactivation aspect of the power cycle were performedfrom a non-user activated operation (e.g., availability of using thecompanion relationship over the short-range communication protocol) andthe re-activation aspect of the power cycle were also performed from anon-user activated operation (e.g., the UE 110 moving away from the UE112 outside an operating range of the short-range communication protocolsuch that the baseband is used to establish a connection to the LTE-RAN122), the reason for the power cycle may be considered a non-useractivated operation.

Based on the reason for the baseband to be power cycled or moregenerally for the data in the allocated section of the temporary memory210A associated with the connection application 235 to be deleted, thestate application 245 may perform subsequent operations and/or instructthe connection application 235 and/or the recording application 240 toperform subsequent operations. Furthermore, the mechanism according tothe exemplary embodiments may also consider how to perform thesubsequent operations when the reason is a non-user activated operationbased on whether a persistent rejection cause is a non-fatal cause or afatal cause.

As noted above, when the reason for the baseband to be power cycled isbased on a user activated operation, there may be an assumption that theuser intentionally power cycled the baseband. For example, the user mayhave reason to attempt another registration procedure if a rejectioncause was previously provided by the LTE-RAN 122 but the registrationprocedure should have been successful (e.g., a SIM refresh). In anotherexample, the user may have replaced an invalid SIM card with a new validSIM card (e.g., a SIM removal). The state application 245 may beconfigured with this assumption. Accordingly, any persistent rejectioncause that may be stored in the persistent memory 210B may be ignored.The persistent rejection cause that may be stored in the persistentmemory 210B may also be deleted if the IMSI or other SIM detailsassociated with the persistent rejection cause are identified asdifferent from a current IMSI or current SIM details. Therefore, thestate application 245 may instruct the connection application 235 toproceed with performing the connection operations including theregistration procedure with the LTE-RAN 122. When power cycled, theconnection application 235 may have been allocated a section of thetemporary memory 210A. However, since this allocated section is empty,the connection application 235 may proceed as if there is no historicalinformation.

The state application 245 may also instruct the recording application240 to perform a subsequent operation. In addition to the storagefunctionalities described above for the recording application 240, therecording application 240 may also perform a deletion functionality.Specifically, when the reason for the baseband being power cycled is auser activated operation, the state application 245 may instruct therecording application 240 to perform the deletion functionality todelete any persistent rejection cause stored in the persistent memory210B. Again, with the above assumption that the user power cycled thebaseband intentionally, any previously experienced rejection from theregistration procedure may be ignored and thus any result fromperforming the registration procedure may also be ignored. It is notedthat the state application 245 may instruct the recording application240 to perform this deletion functionality prior to instructing theconnection application 235 to proceed with the connection operations.

When the reason for the baseband to be power cycled is based on anon-user activated operation, the assumption associated with reasonbeing the user activated operation is no longer present. Accordingly,any persistent rejection cause that may be stored in the persistentmemory 210B may be relevant to the state of the UE 110 upon the basebandbeing re-activated. Again, when power cycled, the connection application235 may have been allocated a section of the temporary memory 210A.However, prior to instructing the connection application 235 to performsubsequent connection operations, the state application 245 may instructthe recording application 240 to push data from the persistent memory210B into the temporary memory 210A, specifically to the allocatedsection associated with the connection application 235. Accordingly, aninitial operation of the state application 245 for this functionalitymay be to determine whether there is any persistent rejection causestored in the persistent memory 210B. If no persistent rejection causeis found, the state application 245 may proceed in a substantiallysimilar manner as if the reason for the baseband being power cycled wasa user activated operation. However, if a persistent rejection cause isfound, the state application 245 may proceed in a different manner andthis manner in which this functionality is performed may be based onwhether the persistent rejection cause stored in the persistent memory210B is a non-fatal cause or a fatal cause.

When the state application 245 identifies that the persistent rejectioncause stored in the persistent memory 210B is a non-fatal cause, thestate application 245 may first determine if the persistent rejectioncause is still valid. As noted above, the rejection cause may be storedin the persistent memory 210B with associated information such as timerelated information and identity related information.

In a first example of validating the persistent non-fatal cause, thestate application 245 may determine if a stored timestamp associatedwith the non-fatal cause indicates that the list of forbidden LA/RA/TAis no longer valid. The timestamp may be compared to the associatedtimer when the list was created where the timer indicates for how longthe list is to remain valid. Accordingly, if the persistent non-fatalcause had been persisted for a duration beyond the timer based on thetimestamp and a current time, the state application 245 may determinethat the non-fatal cause is no longer valid and not to be used.Therefore, the state application 245 may proceed in a substantiallysimilar manner as if the reason for the baseband being power cycled wasa user activated operation. However, if the persistent non-fatal causeis still valid, the state application 245 may perform further operationsincluding instructing the recording application 240 to push thepersistent non-fatal cause from the persistent memory 210B to thetemporary memory 210A and then instructing the connection application235 to perform the connection operations. Once the recording application240 has pushed the data into the allocated section of the temporarymemory 210A corresponding to the connection application 235, the stateapplication 235 may also instruct the recording application 240 todelete the data corresponding to the persistent non-fatal cause from thepersistent memory 210B.

In a second example of validating the persistent non-fatal cause, thestate application 245 may determine whether details of a current SIMmatch details of the SIM associated with the persistent non-fatal cause.For example, the SIM may have associated details that include the IMSI,the ICCID, etc. Since the persistent non-fatal cause was based on theSIM having these associated details, subsequent use of the persistentnon-fatal cause should also only apply when the current SIM has the samedetails. Accordingly, if the persistent non-fatal cause has differentSIM details from the current details of the SIM of the UE 110, the stateapplication 245 may determine that the non-fatal cause is no longerapplicable and not to be used. Therefore, the state application 245 mayproceed in a substantially similar manner as if the reason for thebaseband being power cycled was a user activated operation. However, ifthe persistent non-fatal cause has matched SIM details to the currentdetails of the SIM of the UE 110, the state application 245 may performfurther operations including instructing the recording application 240to push the persistent non-fatal cause from the persistent memory 210Bto the temporary memory 210A and then instructing the connectionapplication 235 to perform the connection operations. Once the recordingapplication 240 has pushed the data into the allocated section of thetemporary memory 210A corresponding to the connection application 235,the state application 235 may also instruct the recording application240 to delete the data corresponding to the persistent non-fatal causefrom the persistent memory 210B.

It is noted that the state application 245 using the above manners ofvalidating the non-fatal cause is only exemplary. The exemplaryembodiments may be configured such that the state application 245 mayutilize other forms of validating the persistent non-fatal cause storedin the persistent memory 210B. Furthermore, the state application 245may utilize any combination or all of the manners of validating thenon-fatal cause. Specifically, if any of the manners of validating wereto indicate that the persistent non-fatal cause were invalid, the stateapplication 245 may assume that the persistent non-fatal cause is nolonger valid. For example, if the persistent non-fatal cause were stillvalid based on the timer but invalid based on the SIM details, the stateapplication 245 may determine that the persistent non-fatal cause isinvalid.

When the state application 245 identifies that the persistent rejectioncause stored in the persistent memory 210B is a fatal cause, the stateapplication 245 may first determine if the persistent rejection cause isstill valid. Again, the rejection cause may be stored in the persistentmemory 210B with associated information such as time related informationand identity related information. The state application 245 mayinitially wait for the SIM to become ready. Once ready, the stateapplication 245 may utilize a substantially similar operation as thesecond example described above for validating the persistent non-fatalcause. Specifically, the state application 245 may determine whether thesame SIM and/or the same conditions are present in the UE 110 after thebaseband has been power cycled. It is noted that the use of when the SIMis ready triggering the functionality of the state application 245 forvalidating/invalidating the SIM is only exemplary. For example,according to other exemplary embodiments, the state application 245 mayperform its functionality at other times (e.g., when attempting to campon a network).

When the persistent rejection cause is a fatal cause, the stateapplication 245 may perform further operations different than when thepersistent rejection cause is a non-fatal cause. When the SIM detailsand conditions of the UE 110 at the time the fatal cause was receivedare different from the current SIM details and/or the current conditionsof the UE 110, the state application 245 may proceed in a substantiallysimilar manner as if the reason for the baseband being power cycled wasa user activated operation. The state application 245 may also instructthe recording application 240 to delete the data corresponding to theinvalidated SIM in the persistent memory 210B. However, when the SIMdetails and conditions of the UE 110 at the time the fatal cause wasreceived is the same as the current SIM details and current conditionsof the UE 110, the state application 245 may determine that the SIM isto be invalidated again. Accordingly, the state application 245 mayinstruct the recording application 240 to push the marked indicationthat the SIM is invalid from the persistent memory 210B to the temporarymemory 210A. Thereafter, the state application 245 may instruct theconnection application 235 to proceed with the connection operations.However, when the connection application 235 checks its allocatedsection in the temporary memory 210A and detects that the SIM has beenmarked as invalidated, the connection application 235 may terminate theconnection operations before the registration procedure is eveninitiated.

In view of the above mechanism according to the exemplary embodiments,the UE 110 may perform connection operations in a more efficient mannerthat increases power conservation when scenarios arise where results ofprevious attempts in performing a registration procedure are persisteddespite operations having been performed that delete these results fromthe temporary memory 210A. By utilizing the mechanism according to theexemplary embodiments, the UE 110 may avoid unnecessary registrationattempts on forbidden LA/RA/TA upon disconnecting with the companion UE112, avoid unnecessary registration attempts on networks that havealready invalidated the SIM, and generally save power and improveperformance.

FIG. 3 shows a method 300 for persisting rejection cause data whileregistering with a network according to the various exemplaryembodiments described herein. The method 300 relates to a first aspectof the mechanism according to the exemplary embodiments where rejectioncauses received from the LTE-RAN 122 are redundantly stored in thememory arrangement 210. The method 300 may be performed by theconnection application 235 and/or the recording application 240. Themethod 300 will be described with regard to the network arrangement 100of FIG. 1 and the UE 110 of FIG. 2.

In 305, the UE 110 transmits a request to register with the LTE-RAN 122.That is, the connection application 235 performs connection operationsincluding a registration procedure to connect to the LTE-RAN 122 and/orutilize services and features such as from the IMS 150. The UE 110 maytransmit various information including identification information (e.g.,details of the SIM).

In 310, the UE 110 receives a response from the LTE-RAN 122 as towhether the request has been accepted and the registration has beensuccessful. If the LTE-RAN 122 has not rejected the request, the UE 110continues to 315 where the UE 110 performs the connection operations toestablish the connection with the LTE-RAN 122. For example, anyauthentication procedure and/or association procedure may be used.

If the LTE-RAN 122 has rejected the request, the UE 110 continues to 320where the UE 110 determines if the response from the LTE-RAN 122included a non-fatal cause or a fatal cause as a rejection cause. If theLTE-RAN 122 rejected the request and provided a non-fatal cause, the UE110 continues to 325. In 325, the UE 110 stores the non-fatal cause as alist of forbidden LA/RA/TA in an allocated section in the temporarymemory 210A associated with the connection application 235. In 330, theUE 110 stores the corresponding information for the non-fatal cause inthe persistent memory 210B. If the LTE-RAN 122 rejected the request andprovided a fatal cause, the UE 110 continues from 320 to 335. In 335,the UE 110 marks the SIM as illegal in the temporary memory 210A. In340, the UE 110 stores the marking of the invalidated SIM and otherrelevant details into the persistent memory 210B.

It is noted that the method 300 may be an iterative process so long asthe UE 110 is being used or activated. More specifically, while thebaseband remains activated, the method 300 may store or overwriteresults of any connection operation or registration procedure performedby the UE 110.

FIG. 4 shows a method 400 for utilizing persistent rejection cause dataprior to registering with a network according to the various exemplaryembodiments described herein. The method 400 relates to a second aspectof the mechanism according to the exemplary embodiments where rejectioncauses that are persisted may be considered to be used for furtherattempts in performing connection operations. The method 400 may beperformed by the connection application 235, the recording application240, and/or the state application 245. The method 400 will be describedwith regard to the network arrangement 100 of FIG. 1 and the UE 110 ofFIG. 2.

In 405, the state of the baseband is monitored. It may be assumed thatthe baseband is currently deactivated for any of a variety of reasons.Thus, in 410, it is determined whether the baseband has been activated.If the baseband remains deactivated, the method 400 returns to 405 tocontinue monitoring the baseband and determine if the baseband has beenactivated.

If the baseband has been activated, in 415, it is determined how thebaseband has been activated. Specifically, it is determined if thebaseband has been activated with a user activated operation or anon-user activated operation. As described above, the baseband may bedeactivated by different user operations (e.g., deactivation fromrebooting the baseband or UE 110, physically removing the SIM card,etc.) and non-user operations (e.g., using the companion relationshipvia the short-range communication protocol). The baseband maysubsequently be activated by different user operations (e.g.,re-activation from rebooting the baseband or UE 110, replacing the SIMcard and re-activating the UE 110, etc.) and non-user operations (e.g.,disconnecting from the companion UE 112).

If the baseband has been activated with a user activated operation, in420, the method 400 may proceed with an assumption that the baseband wasintentionally power cycled and the data stored in an allocated sectionof the temporary memory 210A is to be purposefully deleted. Accordingly,any rejection cause that may have been received prior to the basebandbeing deactivated may be ignored. Accordingly, if any rejection causehas been persisted in the persistent memory 210B, in 420, the storedfatal rejection cause(s) is/are deleted. In 425, the UE 110 performsconnection operations. In this case, the UE 110 performs the connectionoperations as if no historical information is available.

Returning to 415, if the baseband has been activated with a non-useractivated operation, in 430, it is determined whether there are anypersistent rejection causes stored in the persistent memory 210B. If themethod 300 had been performed prior to the method 400, there may be apersistent rejection cause that may have been stored in the persistentmemory 210B. In contrast, if previous registration procedures weresuccessful or the baseband had not been activated previously, there maynot be any persistent rejection cause. If it is determined that there isno persistent rejection cause in the persistent memory 210B, in 425, theUE 110 performs connection operations. In this case, the UE 110 performsthe connection operations as if no historical information is available.

Returning to 430, if it is determined that there is a persistentrejection cause in the persistent memory 210B, in 435, it is determinedwhether the persistent rejection cause is valid. As described above, itmay be determined whether the persistent rejection cause is valid basedon associated information stored with the persistent rejection cause atthe time the rejection cause was received from the LTE-RAN 122. Asdescribed above, if the persistent rejection cause is a non-fatal cause,the validation may be performed based on time information, identityinformation, a combination thereof, etc. If the persistent rejectioncause is a fatal cause, the validation may be performed based onidentity information and whether the current conditions of the UE 110match the conditions at the time the fatal cause was received. If thepersistent rejection cause is invalid, in 425, the UE 110 performsconnection operations. In this case, the UE 110 performs the connectionoperations as if no historical information is available.

If the persistent rejection cause is valid, in 440, the persistentrejection cause is pushed from the persistent memory 210A to theallocated section in the temporary memory 210B associated with theconnection application 235. As described above, when the persistentrejection cause is a non-fatal cause, the forbidden list of LA/RA/TA maybe pushed into the temporary memory 210A. When the persistent rejectioncause is a fatal cause, the marking that the SIM is illegal may be movedto the temporary memory 210A. Subsequently, in 425, the UE 110 performsconnection operations. In this case, the UE 110 performs the connectionoperations by accessing the stored data in the allocated section of thetemporary memory 210A and proceeds by considering the rejection cause.For example, with a non-fatal cause, the UE 110 may perform theregistration procedure if the current LA/RA/TA is different from theLA/RA/TA of the non-fatal cause. In another example, the UE 110 mayprevent any registration procedure from being performed if the SIM ismarked as illegal from a rejection cause being a fatal cause.

The exemplary embodiments provide a device, system, and method ofpersisting a rejection cause as a result of performing connectionoperations with a network. The persisting of the rejection cause may beachieved by redundantly storing the rejection cause in both a temporarymemory and a persistent memory. Thus, if a baseband is power cycled orthe data in the temporary memory becomes deleted, the persistentrejection cause in the persistent memory may be used when the basebandis re-activated. When scenarios arise where the persistent rejectioncause is still applicable, the UE may conserve power and improveperformance by preventing the performance of connection operations thatresult in a rejection.

Those skilled in the art will understand that the above-describedexemplary embodiments may be implemented in any suitable software orhardware configuration or combination thereof. An exemplary hardwareplatform for implementing the exemplary embodiments may include, forexample, an Intel x86 based platform with compatible operating system, aWindows OS, a Mac platform and MAC OS, a mobile device having anoperating system such as iOS, Android, etc. In a further example, theexemplary embodiments of the above described method may be embodied as aprogram containing lines of code stored on a non-transitory computerreadable storage medium that, when compiled, may be executed on aprocessor or microprocessor.

It will be apparent to those skilled in the art that variousmodifications may be made in the present invention, without departingfrom the spirit or the scope of the invention. Thus, it is intended thatthe present invention cover modifications and variations of thisinvention provided they come within the scope of the appended claims andtheir equivalent.

What is claimed is:
 1. A method, comprising: at a device that isconfigured to establish a connection to a network, the device comprisinga memory arrangement including a temporary memory and a persistentmemory, the device using the data stored in the temporary memory whenperforming operations associated with registering with the network:transmitting a first request to the network, wherein the first requestcorresponds to a first attempt to register with the network; receiving aresponse to the first request from the network, the response including arejection cause; storing the rejection cause in the temporary memory andin the persistent memory; when a power cycle is detected, determiningwhether there is persistent data in the persistent memory correspondingto a result from the first attempt to register with the network, whereinthe first attempt occurred prior to the power cycle and the persistentdata includes the rejection cause received from the network in responseto the first request; when there is the persistent data in thepersistent memory, determining whether the persistent data is valid touse in a second attempt to register with the network after the powercycle; when the persistent data is valid, generating cause data based onthe persistent data; and storing the cause data in the temporary memoryprior to performing the second attempt.
 2. The method of claim 1,wherein the rejection cause is one of a non-fatal cause or a fatalcause.
 3. The method of claim 2, wherein the non-fatal cause is based onone of a forbidden location area, a forbidden routing area, or aforbidden tracking area.
 4. The method of claim 2, wherein the fatalcause is based on subscriber identity information.
 5. The method ofclaim 1, further comprising: prior to the determining whether there isthe persistent data in the persistent memory, determining whether thepower cycle is performed based on one of a user activated operation anda non-user activated operation.
 6. The method of claim 5, furthercomprising: when the power cycle is performed based on the useractivated operation, performing the second attempt prior to thedetermining whether there is the persistent data in the persistentmemory.
 7. The method of claim 5, wherein the user activated operationis one of rebooting the device, rebooting a baseband of the deviceassociated with the network, or physically replacing a subscriberidentity module (SIM) card of the device.
 8. The method of claim 5,wherein the device is further configured to establish a connection to afurther device via a short-range communication pathway.
 9. The method ofclaim 8, wherein the non-user activated operation for the power cycle iswhen the device establishes the short-range communication pathway anddeactivates a baseband of the device associated with the network thensubsequently disconnects the short-range communication pathway andre-activates the baseband of the device.
 10. The method of claim 1,further comprising: determining associated information of the devicewhen the rejection cause is received; and storing the associatedinformation in the persistent memory.
 11. The method of claim 10,wherein the associated information is based on a time the rejectioncause is received.
 12. The method of claim 11, wherein the associatedinformation is one of a timestamp of when the rejection cause isreceived, a timer associated with how long the rejection cause is valid,an international mobile subscriber identity (IMSI), an integratedcircuit card identifier (ICCID), or a combination thereof.
 13. Themethod of claim 11, wherein the determining whether the persistent datais valid is based on the associated information and current informationof the device at a time when the power cycle is detected.
 14. A device,comprising: a transceiver; a memory arrangement including a temporarymemory and a persistent memory; a baseband processor configured inconjunction with the transceiver to establish a connection to a network,wherein the baseband processor uses data stored in the temporary memorywhen performing operations associated with registering with the network;and an applications processor configured to detect a power cycle of thebaseband processor, when the power cycle is detected, the applicationsprocessor determining whether there is persistent data in the persistentmemory corresponding to a result from a first attempt to register withthe network prior to the power cycle, the persistent data including arejection cause received from the network for the first attempt,wherein, prior to determining whether there is persistent data in thepersistent memory, the applications processor determines whether thepower cycle was performed based on one of a user activated operation anda non-user activated operation, wherein, when there is the persistentdata in the persistent memory, the applications processor determineswhether the persistent data is valid to use in a second attempt toregister with the network after the power cycle, wherein, when thepersistent data is valid, the applications processor generates causedata based on the persistent data, and wherein, the applicationsprocessor stores the cause data in the temporary memory prior to thebaseband processor performing the second attempt.
 15. The device ofclaim 14, wherein the rejection cause is one of a non-fatal cause or afatal cause, the non-fatal cause being based on one of a forbiddenlocation area, a forbidden routing area, or a forbidden tracking area,the fatal cause is based on subscriber identity information.
 16. Thedevice of claim 14, wherein when the power cycle is performed based onthe user activated operation, the baseband processor performs the secondattempt prior to the determining whether there is the persistent data inthe persistent memory.
 17. The device of claim 16, wherein thetransceiver is further configured to establish a further connection to afurther device via a short-range communication pathway.
 18. The deviceof claim 17, wherein the power cycle is from establishing theshort-range communication pathway and deactivating the basebandprocessor then subsequently disconnecting the short-range communicationpathway and re-activating the baseband processor.
 19. A method,comprising: at a device that is configured to establish a connection toa network, the device comprising a memory arrangement including atemporary memory and a persistent memory, the temporary memory deletingdata stored therein after a power cycle, the persistent memorypersisting data stored therein after the power cycle, the device usingthe data stored in the temporary memory when performing operationsassociated with registering with the network: transmitting a request tothe network wherein the request corresponds to a first attempt toregister with the network; receiving a response to the request from thenetwork; when the response includes a rejection cause indicating therequest is rejected, storing the rejection cause in both the temporarymemory and the persistent memory, wherein, after a power cycle, therejection cause is capable of being used in a further request to thenetwork to register with the network.